Once the requirements analysis is completed, Delivery Team must define the functional and technical changes for the received maintenance change request. While defining the functional changes, the Delivery Team must determine and document:

• Functional enhancements to the components that need to be modified
• Functional specifications of the new components that need to be developed
• Changes to interfaces (both internal and external)
• Changes to other components (including programs, job flows, databases, file layouts, etc.).

Design changes must also include the creating or updating data flow diagrams, schematics, control flow diagrams, class diagrams, sequence diagrams, physical data design, program specifications, stored procedures, etc.

Technical changes must be defined for every new program, and updated for all existing programs. While defining the technical changes, Delivery Team must focus on the changes to be made to a specific program rather than focusing on the entire functionality of the program. This level of detailing is done when there are significant changes in the programs. The technical design must include details of the impacted modules, program overview, screen layout, report layout, changes in data structures, etc.

A peer review must be done on the design document to confirm that the design changes are aligned with the baselined requirements. This task may not be applicable for testing and bug fixing nature of maintenance change requests.